N4 supports EDIFACT standard COHAOR message, release D & version 04B.
COHAOR is used for generic inventory updates announced by trading partners to terminals, to either create or update existing unit details such as special stow code, hazards, reefer temperature, Trucking Company, etc.
This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. The Terminal will receive COHAOR message from shipping lines/shipping agents/freight forwarders to announce about container special handling instruction for dangerous goods on it.
The following sections of this document explain how COHAOR message is handled in N4 and scope of its implementation.
COHAOR is primarily used for updating stow instructions and hazards information of units.
It may contain:
List of containers
Hazards information and Stow instructions of each container
Line operator, vessel details for identifying the unit
COHAOR Inbound Supported Segments
As per EDIFACT standard, Cohaor supports Original,Replace,Cancel function codes.
|
Segment ID |
Supported Qualifier |
Element Description |
Supported in N4? |
|---|---|---|---|
|
UNH |
|
Message Header |
Will get message ,version,release and message reference number |
|
BGM |
|
Beginning of Message
|
Following function codes are supported currently 1 - Cancellation 5 - Replace 9 - Original |
|
DTM |
|
Date/Time/Period To specify date, and/or time, or period. |
This segment is available in dic but not used in built-in map |
|
FTX |
|
Free Text |
This segment is available in dic but not used in built-in map |
|
RFF |
|
Reference |
This segment is available in dic but not used in built-in map |
|
DTM |
|
Date/Time/Period To specify date, and/or time, or period. |
This segment is available in dic but not used in built-in map |
|
NAD |
|
Name and Address To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207. |
This segment is available in dic but not used in built-in map |
|
CTA |
|
Contact Information |
This segment is available in dic but not used in built-in map |
|
COM |
|
Communication Contact |
This segment is available in dic but not used in built-in map |
|
EQD |
CN |
Equipment Details |
supported |
|
RFF |
|
Reference |
This segment is available in dic but not used in built-in map |
|
DTM
|
|
Date/Time/Period To specify date, and/or time, or period |
This segment is available in dic but not used in built-in map |
|
LOC |
|
Place/Location Identification |
This segment is available in dic but not used in built-in map |
|
FTX |
|
Free Text |
This segment is available in dic but not used in built-in map |
|
GOR |
|
Governmental Requirements |
This segment is available in dic but not used in built-in map |
|
HAN |
|
Handling Instructions |
Supported to map stow intructions |
|
MEA |
|
Measurements |
This segment is available in dic but not used in built-in map |
|
PCD |
|
Percentage Details |
This segment is available in dic but not used in built-in map |
|
TDT |
|
Transport Information |
Supported to map outbound vessel visit |
|
DTM |
|
Date/Time/Period To specify date, and/or time, or period |
This segment is available in dic but not used in built-in map |
|
RFF |
|
Reference |
This segment is available in dic but not used in built-in map |
|
LOC |
9 - loadPort 11 - dischargePort |
Place/Location Identification |
Supported |
|
DTM |
|
Date/Time/Period To specify date, and/or time, or period |
This segment is available in dic but not used in built-in map |
|
NAD |
|
Name and Address To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207. |
This segment is available in dic but not used in built-in map |
|
CTA |
|
Contact Information |
This segment is available in dic but not used in built-in map |
|
COM |
|
Communication Contact |
This segment is available in dic but not used in built-in map |
|
DGS |
|
Dangerous Goods |
Supported to map hazard details |
|
FTX |
|
Free Text |
This segment is available in dic but not used in built-in map |
|
MEA |
|
Measurements |
This segment is available in dic but not used in built-in map |
|
CTA |
|
Contact Information |
This segment is available in dic but not used in built-in map |
|
COM |
|
Communication Contact |
This segment is available in dic but not used in built-in map |
|
TMP |
|
Temperature |
This segment is available in dic but not used in built-in map |
|
RNG |
|
Range Details |
This segment is available in dic but not used in built-in map |
COHAOR Inbound N4 Built-in Map
A new built-in map with map id "COHAOR_D_04B_IN" is added to N4. This map can be used to convert the cohaor edi file into Navis standard cohaor.xml. This xml in turn used for further processing.
Following are the related files, part of N4 application and can be downloaded:
cohaor_D_04B.mgt - GoXml map
cohaor.dic - Edifact standard dictionary
inventoryUpdates.xsd - Navis standard xml schema
ARGOCORE014 - This is for auto creation of vessel visits if the vessel is not found.
ARGOCORE015 - This is to check if the category given in the EDI is accurate or not
Step - 1: Create a session for Cohaor message.
Posting of COHAOR Inbound EDI message
Step - 2: Post Cohaor Original message.
Ensure batch is completed without any error message and unit is created with hazard and stow informations.
Step - 3: Post Cohaor EDI Replace message
Cohaor Replace message posted successfully and hazard and stow instructions are updated, history event is recorded with field changes
Step - 4: Post Cohaor EDI Cancel message
COHAOR Cancel message nullified hazard and stow informations. History event is recorded for cancel message with field changes.
A new poster “InventoryUpdatesPoster” is created for posting the mappings to N4.
The facility is resolved based on:
VesselcallFacility – The user can override this element to provide the facility , against which the unit gets posted.
EDI_FACILITY_FOR_POSTING – User can set the value for this setting at edi session level
Otherwise, the facility is resolved based on the outbound carrier visit.
A new setting has been introduced to determine if the equipment category provided in edi is accurate or not- If not accurate we determine the category based on the port of load,port of discharge,port of transhipment.
Another setting for auto creation of vessel visit is introduced - INV_UPDATES_ALLOW_FOREIGN_VESSEL_VISIT
We record the UNIT_PROPERTY_UPDATE,UNIT_HAZARD_INSERT/UNIT_HAZARD_UPDATE events notes property with the reference number passed in edi.
The poster supports 3 message functions- Original(O),replace(X),cancel(D)
When a replace or cancel message is posted , we validate reference number with the already recorded events (UNIT_PROPERTY_UPDATE/ UNIT_HAZARD_INSERT/UNIT_HAZARD_UPDATE) in the unit and then only post the changes.Only if the reference number matches we proceed to post the changes otherwise we throw a error message.
It provides posting rule support for Stow instructions, Hazards and general rule.
We have extended data quality support for the poster.
Sample Edi File for Original message:
Sample EDI file with Replace Message:
Replace message for the same container with matching reference number.
Sample EDI file for Cancel message:
Cancel message for the same container with matching reference number.
